build_library: fix Exoscale image format, size, and compression#4075
Open
jheidel wants to merge 1 commit into
Open
build_library: fix Exoscale image format, size, and compression#4075jheidel wants to merge 1 commit into
jheidel wants to merge 1 commit into
Conversation
Exoscale requires Custom Templates to be at least 10GB, expects a .qcow2 extension, and Exoscale Custom Templates do not support compressed (.bz2) images. Currently, Flatcar releases an 8GB compressed .img file. This change ensures the output file uses the .qcow2 extension, applies a post-conversion resize to exactly 10G, and disables compression in the release pipeline to match platform requirements and UI prompts. Signed-off-by: Jeff Heidel <jheidel@gmail.com>
tormath1
moved this to ✅ Testing / in Review
in Flatcar tactical, release planning, and roadmap
Contributor
|
Hey @jheidel thanks a lot for your contribution, I kicked-off a CI job to see if everything continues to build correctly but the changes look good from a first look. I was talking about Exoscale support a moment ago, and I'm wondering if the documentation is up-to-date for Exoscale: https://www.flatcar.org/docs/latest/installing/community-platforms/exoscale/ - did you use this documentation? |
tormath1
reviewed
Jun 8, 2026
Contributor
tormath1
left a comment
tormath1
left a comment
There was a problem hiding this comment.
Can we add a changelog entry in changelog/changes ?
Contributor
|
Great to hear that someone is using Exoscale, as we were very doubtful! Also great to hear that this is (hopefully) the only issue. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix Exoscale image format, size, and compression
Exoscale requires Custom Templates to be at least 10GB, expects a .qcow2 extension, and Exoscale Custom Templates do not support compressed (.bz2) images. Currently, Flatcar releases an 8GB compressed .img.bz file.
This change ensures the output file uses the .qcow2 extension, applies a post-conversion resize to exactly 10G, and disables compression in the release pipeline, matching that of similar platforms (scaleway, etc).
This fixes flatcar/Flatcar#2163
How to use
Reviewers can verify that the generated .qcow2 image can be directly used by Exoscale Custom Template and that this instance can be used to create a new compute instance with 10G disk size.
Testing done
The changes were verified using the Flatcar SDK:
Verify image metadata:
Real-world test: The resulting image was hosted on a public web server and successfully imported into Exoscale's 'Add Custom Template' UI without any manual renaming, resizing, or decompression required.
CI: https://jenkins.flatcar.org/job/container/job/packages_all_arches/163/cldsv/